This command gets the Finder's selected files and folders. This was written for the 7.x Finder (including the scriptable Finder), but using it with newer Finders could cause it to fail. It has problems using fake files, like PowerTalk catalogs and mailboxes, and probably other things like that. It checks for any flavor of System 7, which means it could break on versions after 7.5.3, which works. It definately won't work for much longer.

You should use the scriptable Finder's "selection" property instead of this command. This is still useful if you are supporting or using older systems.

You can place script applications in the Apple Menu Items folder or with either OSA Menu or OtherMenu's script menu and use the "finder selection" function to have your script operate on the selected files. Way cool.

Compared to the Scriptable Finder, which returns a list of object specifiers, this returns a list (or just one) of aliases.

example:

finder selection

copyFile, deleteFile, moveFile & renameFile:

These commands work on files and lists of files. You can use file references (file "disk:folder:foo"), pathname strings or aliases to specify the files and folders for these commands. In contrast to the Scriptable Finder, these commands run faster, don't put up progress dialogs, batch their operations and use temporary memory when available.

You cannot use Finder object references with these commands. You need to coerce them to strings or aliases in order to pass them to these commands.

RenameFile can only change the name of a file or folder. The source is a file or folder reference, alias or pathname and the destination is just the new name. It cannot be a new location.

DeleteFile is permanent and immediate. Be very careful with it. I recommend using "moveFile foo to (path to trash)" if you are at all worried or inclined toward cautiousness. This will only delete empty folders unless the "without safety net" parameter is used. Then this will delete full folders, so be very very careful with this parameter. This command also has an option "with unlocking" which allows it to delete locked files, but if this option isn't specified and the "without safety net" is used and there's locked files in a folder, then error 27364 will be returned and only the locked files will not be deleted, which is how the trash works too.

MoveFile only moves files or folders around on the disk they are on. It does not copy between disks. It cannot rename or replace files either. The destination is a folder, which you can specify either with a file reference, an alias or as a pathname string.

CopyFile uses temporary memory if available and tries to copy the file in 1 pass for maximum speed. The source may be either a file or a folder, or list of files and/or folders. The destination may be either a file or folder to copy to, unless the source is a folder in which case the destination must be a folder. The source folder will be copied into the destination folder.

You cannot replace an existing folder so the replacing parameter is ignored when copying folders. You cannot rename a folder while copying it, so you'll need to use renameFile after the copy completes.

If you try to replace a busy file, the copy will succeed but the busy file will be left in the temporary items folder and will appear in the Rescued Items folder in the trash after the next restart. It will then be deleted the next time you empty the trash.

example:

copyFile "disk:folder:foo" to "disk2:folder:bar" with replacing
copyFile "disk:folder:foo" to "disk2:folder:bar" replacing yes
copyFile "disk:folder:foo" to "disk2:folder:bar" without replacing
copyFile "disk:folder:foo" to "disk2:folder:bar" replacing ask
deleteFile "disk:folder:foo"
deleteFile "disk:folder:foo" with unlocking
deleteFile alias "disk:folder:"
deleteFile file "disk:folder:" without safety net
moveFile "disk:folder:foo" to "disk:folder2:"
renameFile alias "disk:folder:foo" to "bar"
copyFile {"disk:folder:foo", alias "disk2:folder:bar:"} to "disk3:folder:"
deleteFile {file "disk:folder:foo", "disk2:folder:bar"}

execute FKEY:

This loads the specified FKEY resource and jumps to it. It does not press command-shift-N, so it will not trigger QuicKeys macros or any function which patches things to run at FKEY-like key combinations.

example:

execute FKEY "Switch-a-roo"
execute FKEY 5

keys pressed:

This returns the GetKey info in the form of a list of key names in string form.

example:

(keys pressed) contains "option"
(keys pressed) = {"option", "command"}

screen list:

set screens to:

machine environment:

Machine Environment returns a keyworded record object of common machine information from Gestalt. You can also feed it a Gestalt selector and it will return the long word response. This provides complete access to all of the Gestalt functions that exist. You can use the "check bit" parameter to return a boolean which tells if that bit is on. Bits are numbered from 1 to 32 with number 1 being the lowest or rightmost bit. In this way you can get any information from Gestalt.

That this command will return an error of -5551 if the Gestalt selector code is not installed.

The environment info object provides these properties by default:

machine type - string - The name of the Macintosh model (less specific in recent systems).

CPU type - string - The CPU installed.

System version - string - The current System version.

FPU - boolean - Does this machine have an FPU?

PowerPC - boolean - Whether this machine is a PowerPC.

Color Quickdraw - boolean - Does this machine have color Quickdraw?

Data Access Manager - boolean - Does this machine have the Data Access Manager installed?

software power off - boolean - Does this machine turn off when shutdown?

logical RAM - integer - Amount of RAM available to the system.

physical RAM - integer - Amount of RAM installed in this machine.

active scripts - integer - Number of script systems active.

AppleTalk version - extended real - The current AppleTalk version.

keyboard - string - The name of the main keyboard.

virtual memory - boolean - Is virtual memory on?

scriptable Finder - boolean - Is the scriptable Finder present?

Open Transport - boolean - Is Open Transport installed?

ethernet address - string - The hardware ethernet address.

owner name - string - The owner name in sharing setup.

sharing name - string - The machine name in sharing setup.

Both this and "keys pressed" use STR# resources if you are inclined to localize them. The machine info is a subset of the available Gestalt selectors. If you have need of others, let me know and I might include them in a future version, although you can get raw information for any gestalt selector directly.

example:

machine environment

{machine type:"Power Mac 8500/120", CPU type:"604", System version:7.6, 
FPU:true, PowerPC:true, Color Quickdraw:true, Data Access Manager:true, 
software power off:true, logical RAM:67108864, physical RAM:67108864, 
active scripts:1, AppleTalk version:60, keyboard:"Extended ADB Keyboard", 
virtual memory:false, scriptable Finder:true, Open Transport:true, 
ethernet address:"00:05:02:E0:52:C9", owner name:"Jon Pugh", 
sharing name:"Power Period"}

scriptable Finder of (machine environment)
machine environment "code"
machine environment "code" check bit 0

clipboard info, the clipboard & set the clipboard to:

sound volume & set sound volume to:

Both of these use a number between 0 and 7 for the volume, just like everyone else.

example:

set oldVol to sound volume
set sound volume to 5
set sound volume to oldVol

play sound:

This can play sound ('snd ') resources installed in the system or the current open files by either name or id number. It can also play sound resources out of files and out of AppleScript variables (typically accessed via the clipboard). You cannot interrupt a sound in progress in this version and the sounds are played synchronously. This command is a small improvement on Donald's sample code from the Language Reference Manual.

example:

play sound "I'm sorry Dave..."

run script resource:

This matches the AppleScript Run Script command but works on resources instead of files. This allows you to bundle several scripts (typically from other OSA components such as QuicKeys) into a single script file or application. I've used it to place the 'scpt' resources from QuicKeys scripts into an applet and run them from there.

There is a problem with having more than 1 'scpt' resource per file and that is the Script Editor. It finds the script to display by using Get1IndResource('scpt', 1) which can return the wrong resource if you have several. If you are literate with ResEdit you can make sure the proper script resource is last in the file, but that's less certain than the other technique I recommend, which is to change the script resource's type to 'Scpt' which is not recognized by the Script Editor. You need to copy the script resource as hex data and paste it into a new empty 'Scpt' resource. This way allows no conflicts. Another solution is to use my ScriptServer application (available on Info-Mac & gaea) which allows you to create script resources of any type and id. This makes it simple to create a script application which combines AppleScript and QuicKeys scripts. You can even record a QuicKeys script, decompile it with ScriptServer, edit it and recompile it as a piece of a script application.

Yet another option is simply to record a QuicKeys script, copy it and paste the text into your AppleScript script with the "run script foo in QuicKeys" command with foo as your text or a variable with text in it. This works well with simple scripts and doesn't require this osax. Unfortunately, the Run Script 1.1 osax has a memory leak when doing this. Running a compiled script resource is marginally faster too.

You can reference script resources by name or number.

example:

run script resource "Flail madly"

free memory:

This returns the current value of the function FreeMem. It shows the amount of free memory available in the current application's current heap. Useful for finding memory leaks. You can also specify which heap you would like info about with the constants appZone and sysZone.

example:

free memory
free memory sysZone

the ticks:

This returns the current value of TickCount. This is useful for timing functions from scripts. Unfortunately, this opens the resource file for Jon's Commands every time and thus affects your timing slightly, making it more useful for large timings where the overhead is less instead of small ones.

This example is a script object which can record a series of times using the ticks. Include it at the beginning of your script and call it's methods.

script SmartTimer
  property IMrunning : false
  property startTime : 0
  property endTime : 0
  property timeLog : {}
  
  on startTimer()
    if IMrunning then
      error "Timer already running"
    end if
    try
      set startTime to the ticks
      set IMrunning to true
    on error theMsg number -1708
      error "You need Jon's Commands installed to use this script object."
    end try
  end startTimer
  
  on stopTimer()
    if not IMrunning then
      error "Timer is not running"
    end if
    set endTime to the ticks
    set IMrunning to false
    set elapsedTime to endTime - startTime
    set timeLog to timeLog & {elapsedTime}
    return elapsedTime
  end stopTimer
  
  on averageTime()
    set sum to 0
    set n to number of items of timeLog
    repeat with i in timeLog
      set sum to sum + i
    end repeat
    return sum / n
  end averageTime
  
  on getLog()
    return timeLog
  end getLog
  
  on clearLog()
    set timeLog to {}
  end clearLog
end script

walk folders:

This makes file processors very simple and fast. It takes a list of files and folders and a script. It then walks through them all and sends each file to an open handler in the script. Note that as of version 1.3.4, walk folders steps backwards through directories (reverse alphabetical order) so that you can delete files without affecting the subsequent indexing. It is possible to make this be an option if people whine enough.

The "only using files of type" parameter allows you to specify one or more file types that will be operated on. Only files of the types specified will be sent to your script parameter. The types are 4 character strings with the obscure codes you will have to find out about. Normal choices are things like "APPL", "osax" and "TEXT".

In addition, there are 2 boolean parameters, "using files" and "using folders". "using files" defaults to true and causes all files to be run through the script. "using folders" defaults to false and causes all folders to be run through the script. You can set them to true or false by using "with using folders" and/or "without using files".

example:

on open (theFiles)
  script foo
    property fileList : {}
    on open (theFile)
      copy theFile as string to end of fileList
      -display dialog theFile as string
      return fileList
    end open
  end script
  set fl to walk folders theFiles with script foo only using files of type {"TEXT", "osas"}
  display dialog (number of items of fl) as string
end open

set cursor to:

This allows you to change the current cursor to indicate a busy script. It is problematic since the front application can change it right back, and many do, but it can be very useful nonetheless.

You can use the five standard cursors; arrow cursor, watch cursor, I beam cursor, cross cursor & plus cursor, plus a busy cursor which spins. You can also specify the name or number of a CURS resource or, using the "with cursor list" parameter, an acur resource. Subsequent calls with the "busy cursor" will increment this cursor one step.

The busy cursor keeps an acur and all the CURS resources in memory between calls. The "with cursor list" parameter is only necessary on the first call and will reinitialize the cursor if always supplied (i.e. the cursor will not spin). You can clear this memory by setting the cursor to something other than a busy cursor (i.e. watch cursor or arrow cursor).

These are the busy cursors available in Jon's Commands, use their names or numbers (names are probably less likely to conflict with other resources):

This does not support color cursors yet.

example:

set cursor to busy cursor with cursor list "Zen Cursor"
repeat
  set cursor to busy cursor
end repeat
set cursor to watch cursor

AE user interaction level:

This allows you to get and set the AppleEvent manager's user interaction level. This way you can allow interaction from remote machines or disallow interaction from local scripts. In order for this to work, the program which is doing the interaction must explicitly check if interaction is allowed. Hopefully all scriptable applications do, but reality is seldom so kind.

This returns the current state and then optionally sets it to the new state.

The main drawback with the user interaction level is that you cannot completely turn off user interaction in the current application from a script run by OSA Menu or an application's script menu. Since the lowest interaction level is "AE interact with self" and a script running by OSA Menu or an application itself is sending events to itself, this is always allowed so the app can put up dialogs.

Applications need to support a "never interact" mode explicitly. Apple's PhotoFlash does (shameless plug from one of the authors), but it's only available if you buy a QuickTake camera.

example:

set oldLevel to AE user interaction level AE interact with self
AE user interaction level oldLevel

choose color:

This function displays the standard color picker and returns an RGB color value. You can specify the prompt and the initial color. RGB colors can be specified via a list of three numbers between 0 and 65535. It's actually a 3 word data value which can be coerced to and from a list. This will throw error 9876 if run on an old 68000 Macintosh without color Quickdraw.

example:

choose color
set newColor to choose color "Pick your favorite color:" starting color {0, 0, 0}

example script:

-- paste an HTML color reference into BBEdit
property lastColor : {35000, 35000, 35000}
set lastColor to choose color "Choose a background color:" starting color lastColor
set s to "#"
set a to "0123456789ABCDEF"
repeat with i in lastColor
  set q to round (i / 65535 * 256)
  if q > 255 then set q to 255 -- limitation of HTML, FF is the brightest
  set h to q div 16
  set l to q mod 16
  set s to s & character (h + 1) of a & character (l + 1) of a
end repeat
tell application "BBEdit 4.0"
  set selected text of window 1 to s
end tell

keyboard lights:

This function returns the current setting of the keyboard lights on an ADB extended keyboard and sets them to whatever you specify, which allows you to do a progress indicator which is not obscured by screen savers. Note that this command can override the setting of the caps lock light so that it may not match the actual keyboard setting. Pressing the caps lock key a few times will reset it.

If a keyboard with lights cannot be found, then this command will throw error 23.

The input and return values can be a list of enums or a number. The list has three possible enums in it, num lock light (1), caps lock light (2), and scroll lock light (4). You can use either the enums or an integer combination of the values in parentheses (from 0 to 7). You can also use any other number to signify no change to the lights but that you want the return value to be an integer.

example:

keyboard lights {num lock light, caps lock light, scroll lock light} -- turn the lights on & return a list
set oldLights to keyboard lights {} -- turn the lights off & return a list
keyboard lights 6 -- caps lock & scroll lock & return an integer
keyboard lights 0 -- all off & return an integer
set oldLights to keyboard lights -1 -- no change but returns an integer

example script:

repeat
  repeat with i from 0 to 7
    keyboard lights i
    repeat 10000 times
    end repeat
    if (keys pressed) is not equal to {} then
      keyboard lights 0
      error number -128
    end if
  end repeat
end repeat

snag object:

This command is a geeky developer tool mostly of use to people writing applications which want to send a single object specifier to another scriptable application, like the Finder, but don't want to either build the object specifier by hand or load AppleScript for this simple task (typically because of the memory requirements). This command allows them to write the object specfier in their script editor like normal and then, using the "snag object" command, save that object specifier to a file. They can then paste this object specifier resource into their application and build a simple GetData event with it as the direct parameter. The results are returned in the reply and everyone's cruising. See the "Snag Object Demo" folder for working example code.

example:

snag object <reference> in <file> id <number> type <string>

example script:

set f to path to desktop as string
tell application "Finder"
  snag object (creator type of processes whose visible = false) ¬
  in file (f & "Test") id 128 type "obj "
end tell

alias information:

This command returns information about aliases. They can be alias variables, alias files, or they can be alias resources in other files. You can specify a specific 'alis' resource by using the id parameter. Without the id parameter, this command looks for id 0 first and then takes the first one it can get via Get1IndResource. If it cannot find an alias, it will throw error 2394.

Normally, this command resolves the alias before it returns any information about it, but this can be troublesome when the alias points to a network server since the server will be mounted, possibly bringing up a login dialog. In order to prevent this, you can specify "without resolving" which will skip this step and the information will be pulled out of the alias without resolving it. Note that this could return incorrect information if the original has been moved or renamed. Also note that the "alias" and "alias was changed" properties of the alias info object are not returned if the alias is not resolved, since these pieces of information require that the resolution succeed.

Beware of passing aliases to aliases to this command when you aren't resolving them. For example:

alias information alias "TRex:Desktop Folder:Netscape alias" without resolving

This command will return the information for the alias pointing to the Netscape alias file, not the alias in the Netscape alias file. You'll need to use a file reference to do that:

alias information file "TRex:Desktop Folder:Netscape alias" without resolving

Finally, even if the alias was changed when it was resolved, it is not updated on disk. You would need to have the scriptable Finder resolve or replace the alias for that to occur. You can accomplish this most easily simply by getting the "original item" of the alias file. That will cause the Finder to update the alias.

The alias info object has these properties:

alias zone name - string - The zone of the original item.

alias machine name - string - The machine name of the original item.

alias volume name - string - The name of the volume that the original item is from.

alias path - string - The full path of the alias.

alias - alias - The alias itself. This is only present if the alias was resolved.

alias was changed - boolean - Was the alias changed when it was resolved? This is only present if the alias was resolved.

example:

alias information <file> id <number> without resolving

example script:

set foo to (path to apple menu items folder as string) & "Control Panels"
alias information foo

load embedded scripting additions:

This command is another geeky developer tool, however this one is for AppleScript application developers who wish to bundle osaxen into their standalone script applications (applets and droplets). This can reduce the installation clutter down to simply installing Jon's Commands instead of a whole slew of scripting additions.

The technique is relatively simple, given an understanding of ResEdit. You simply copy the osax resources, and whatever other resources the osaxen may use (there's no way of telling aside from asking the developer, which you should do anyhow) into your finished applet. Be sure to save this for the last step, since changing the applet with the Script Editor can delete the resources you copied into it. Before you have the resources embedded, make the single "load embedded osaxen resources" call as the first line of your script and then you won't need to have those scripting additions installed in the system, only in your applet.

In the case where a scripting addition is installed in the system and the same one (or a different version of the same one) is in the applet, the one installed in the application by this command will be used, solely because it is in the application's event handler table, which is searched before the system's table where all the other scripting additions are.

This command should only be called once because it loads the 'osax' resources into memory, detaches them and installs them in the event handler table. It does not keep any reference to those memory blocks, so they are not reclaimed until the application quits. Calling this multiple times will install multiple copies and use a potentially significant amount of memory.

As I said before, you'll still need to have Jon's Commands installed in the Scripting Additions folder for this to work. It would take a new applet shell (the code that runs your script) to remove this restriction. You should also make sure that you aren't violating scripting addition author's distribution restrictions.

There's only one parameter to this command and it should generally be used. It is "only the top resource file used" and restricts the resource loading to only the applet, which is the top resource file (excepting Jon's Commands and AppleScript which are opened on top of the script application calling this command). The parameter is a boolean parameter, so it is accessed via the with/without keywords. The default is without, so you only need to use it with "with". With this command and this parameter, I'm betting that I've got the longest 1 parameter event in all of AppleScript.

This will return error 11934 if there are no 'osax' resources to install and 11935 if there is an 'osax' resource with an invalid name.

examples:

load embedded scripting additions
load embedded scripting additions with only the top resource file used

File Coercions:

string to file specification

styled text to file specification

international text to file specification

These coercions allow you to use strings where a program or osax expects a file specification. Note that the AppleScript class "file" is really an object reference, not simply an FSSpec, although it can be coerced to one. You can create an FSSpec by using this command: set x to "disk:folder:file" as «class fss ». They are particularly easy to implement. With these coercions you don't need to worry about them though.

Script Coercions:

script to anything

This coercion allows you to coerce a script, as obtained from the "load script" scripting addition, to any type that it can be decompiled into. Normally, this is text, string or styled text.

Version History:

2.0 - official release
2.0b6 - Removed "with unsafe modes" parameter and added "safe resolution" property instead, as well as adding "resultion index" for more reliable access to the various resolution modes.
2.0b5 - Added "with unsafe modes" to "screen list" command.
2.0b4 - Removed invalid modes and any occurances of a 0 refresh rate from the "supported resolutions" property of "screen list" command. Added SmartTimer to guide file.
2.0b3 - Recompiled "copyFile" and "alias information" commands with MoreFiles 1.4.6, for whatever that is worth. Made "run script resource" return error numbers and messages. Added "safety net" parameter to "deleteFile" command to prevent accidental deletion of full folders. This affects scripts! Added script coercion handler. Reversed the order of this change log.
2.0b2 - Extensive modifications to "screen list" and "set screens to" commands to make screen ids 1 based, add actual screen names, refresh rates and lists of possible resolutions. Unfortunately, dealing with the refresh rate requires Display Manager 2, which is included in System 7.5.3 and available separately. If DM2 is not installed, the "screen list" command will not return refresh rate or supported resolutions and the "set screens to" command will error if you try to change the refresh rate.
2.0b1 - Made "alias information" command take an alias descriptor also instead of only alias files. This could affect scripts since an alias to an alias file will now return info about the alias instead of the alias file. Made "machine environment" command return Open Transport status and hardware ethernet address if OT is running. Added "load embedded scripting additions" command. Reworked docs in HTML. Bumped the version up to 2.0 just for the heck of it.
1.8.1 - official release
1.8.1b3 - Shortened the copyFile temp file name so that it couldn't get too long & recompiled with MoreFiles 1.4.3.
1.8.1b2 - Fixed missing watch cursor from animated cursor in "set cursor to" command. Changed a bunch of the ids for resources just in case since they might conflict with application resources when embedding osaxen. Now they're all in wackier ranges. This could affect scripts! This could affect the "set cursor to" command in your scripts if (and only if) you refer to cursor lists by number instead of by name. Made "play sound" recognize and follow alias files.
1.8.1b1 - Made "machine environment" recognize PowerBook keyboards and 603e, 603ev and 604e processors.
1.8 - official release
1.8b5 - Made "walk folders" return errors from the script properly (they were all -1753 before).
1.8b4 - Made "machine environment" handle missing machine or owner name safely.
1.8b3 - ++futz
1.8b2 - Futzed with it.
1.8b1 - Added "alias information" command.
1.7.2 - official release
1.7.2b1 - Reworked ordering of "walk folder" execution so that deleting files & folders is possible. Made "deleteFile" delete folders recursively.
1.7.1 - official release
1.7.1b2 - Added this comment for you comment aficionados.
1.7.1b1 - Fixed moveFile for multiple files and put away functionality.
1.7 - official release
1.7b4 - Removed the **** to TEXT coercion because of its lack of usefulness and potential for engendering confusion.
1.7b3 - Added a couple more parameters to the "snag object" command. Removed the Display Enabler since it's too big and available seperately.
1.7b2 - Added "snag object" command.
1.7b1 - Added **** to TEXT coercion.
1.6 - official release
1.6b1 - Added "keyboard lights" command.
1.5.1 - official release
1.5.1b1 - Reverted to 1.4's "finder selection" command because the new sc compiler appears to have changed the object layout so that it doesn't match the Finder's objects anymore and thus doesn't work in 1.5. Also ditched the Display Library as it isn't needed.
1.5 - official release
1.5b3 - included Display Enabler for Display Manager 2.
1.5b2 - Added "with unlocking" parameter to "deleteFile" command so it can delete locked files. Made "set screens to" command persistent when running Display Manager 2. Beefed up the examples and moved them to a new file, "Jon's Commands Notes" to avoid the 32K limit of SimpleText.
1.5b1 - Made everything compile with MPW Pro and the new headers. Made "moveFile" support the Finder's Put Away command. Added "Jon's Commands Reference" guide file to the package. Added "set screens to" command.
1.4 - official release
1.4b4 - Fixed "CPU type" and "FPU" to work properly with PowerPC machines and added "PowerPC" property. Added description and examples for "screen list" command to this document. It was always missing and no one noticed.
1.4b3 - Added "owner name" and "sharing name" properties to "machine information" record.
1.4b2 - Added "choose color" command. Wondered if this change log was worth the bother. It's kind of embarassing, but I guess it's educational. I hope. :) Changed the version to 1.4 since we added a command.
1.3.7b1 - Fixed some comments in the dictionary. Changed the "check bit" parameter of "machine environment" command to be zero based instead of one based, making it compatible with Inside Mac. This affects scripts!
1.3.6 - official release
1.3.6b4 - Added "check bit" parameter to "machine environment" command.
1.3.6b3 - Fixed "finder selection" crash when trash is selected. There are probably still problems with selecting PowerTalk or GX items which are not files.
1.3.6b2 - Fixed "walk folders" bug when walking folders; files were fine.
1.3.6b1 - Made replacing parameter on "copyFile" accept yes/no/ask & error when used with directories.
1.3.5 - official release
1.3.5b1 - Fixed "copyFile" bug when copying file to file with a different name.
1.3.4 - official release
1.3.4b4 - Made "copyFile" copy folders too.
1.3.4b3 - Made "copyFile" return better errors when files and directories are missing. Zeroed location when not replacing so that the Finder will put the icon in the first empty spot.
1.3.4b2 - Made "copyFile" fail when copying to a nonexistant directory.
1.3.4b1 - Made "walk folders" command step backwards through folders.
1.3.3 - official release
1.3.3b2 - Fixed "copyFile" problem when replacing a nonexistent file.
1.3.3b1 - Made clipboard commands error when in the background.
1.3.2 - official release
1.3.2b5 - replaced guts of "copyFile" with MoreFiles code. Now it works with drop boxes. Spruced up the readme some more.
1.3.2b4 - honest, this time "copyFile" is fixed. It was FSpDelete that was failing.
1.3.2b3 - made "copyFile" delete the temp file even if FSpExchangeFile fails. Also fixed memory leak in "keys pressed".
1.3.2b2 - added additional acur and CURS resources and spruced up the readme.
1.3.2b1 - added "scriptable Finder" to "machine environment" record.
1.3.1 - official release
1.3.1b1 - made aete unpurgeable to avoid Script Editor dictionary bug.
1.3 - official release
1.3b1 - added "only using files of type" parameter to "walk folders" command.
1.2 - official release
1.2b2 - added "AE user interaction level" function.
1.2b1 - added "set cursor to" command.
1.1.3 - official release
1.1.3b1 - recompiled with debugger breaks off. Ooops.
1.1.2 - official release
1.1.2b1 - made string to fsspec coercion more picky so that it doesn't confuse the "run script" osax.
1.1.1 - official release
1.1.1b3 - fixed error handler in "play sound".
1.1.1b2 - fixed "execute fkey" error handling, twiddled clipboard code to remove debugger calls & clean up the code a bit, fixed "finder selection" when items were on desktop of volumes other than the startup volume & made "walk folders" send an alias instead of a file specification for compatibility with AS 1.0.
1.1.1b1 - fixed "machine environment" property name conflict with "machine" by renaming it "machine type" and actually implemented the "cpu type" property. Also fixed the sample script for "walk folders" above.
1.1 - official release
1.1b3 - added "walk folders" command, made "finder selection" return aliases for AS 1.0 compatibility and made "screen list" work without color QuickDraw.
1.1b2 - fixed bug in "set clipboard to" which could cause changes to the clipboard to be unnoticed and fixed a really minor bug in "execute FKEY" which passed a dirty PC to the FKEY in 24 bit mode.
1.1b1 - added "copyFile" command. Made "moveFile", "deleteFile", "renameFile" & "copyFile" accept lists of files, aliases or pathnames. Added string to file specification coercion.
1.0 - official release.
1.0b5 - added "free memory" and "the ticks" commands.
1.0b4 - added "run script resource" command.
1.0b3 - added 7.1.1 to version check for "finder selection".
1.0b2 - fixed key name in "keys pressed" for PowerBook keyboard.
1.0b1 - first public release